Control methods for a force sensor system

ABSTRACT

A method of controlling a force sensor system to define at least one button implemented by at least one force sensor, the method comprising: receiving a force sensor input; determining a gradient of the force sensor input; and controlling the force sensor system based on the determined gradient.

RELATED PATENTS

The present disclosure relates to U.S. Provisional Patent ApplicationSer. No. 62/842821, filed May 3, 2019 (Attorney Docket NumberP3629USPROV) and U.S. patent application Ser. No. 16/422543, filed May24, 2019 (Attorney Docket Number P3629US00), all of which areincorporated by reference herein in their entireties.

FIELD OF DISCLOSURE

The present disclosure relates to control methods for a force sensorsystem, and in particular to systems and methods for compensating forthe effects of temperature on force sensing systems.

BACKGROUND

Force sensors are known as possible input devices for electronicsystems, and can be used as an alternative to traditional mechanicalswitches.

Many traditional mobile devices (e.g., mobile phones, personal digitalassistants, video game controllers, etc.) include mechanical buttons toallow for interaction between a user of a mobile device and the mobiledevice itself. However, such mechanical buttons are susceptible toaging, wear, and tear that may reduce the useful life of a mobile deviceand/or may require significant repair if malfunction occurs. Also, thepresence of mechanical buttons may render it difficult to manufacturemobile devices to be waterproof.

Accordingly, mobile device manufacturers are increasingly looking toequip mobile devices with virtual buttons that act as a human-machineinterface allowing for interaction between a user of a mobile device andthe mobile device itself. Similarly, mobile device manufacturers areincreasingly looking to equip mobile devices with other virtualinterface areas (e.g., a virtual slider, interface areas of a body ofthe mobile device other than a touch screen, etc.). Ideally, for bestuser experience, such virtual interface areas should look and feel to auser as if a mechanical button or other mechanical interface werepresent instead of a virtual button or virtual interface area.

Presently, linear resonant actuators (LRAs) and other vibrationalactuators (e.g., rotational actuators, vibrating motors, etc.) areincreasingly being used in mobile devices to generate vibrationalfeedback in response to user interaction with human-machine interfacesof such devices. Typically, a sensor (traditionally a force or pressuresensor) detects user interaction with the device (e.g., a finger presson a virtual button of the device) and in response thereto, the linearresonant actuator may vibrate to provide feedback to the user. Forexample, a linear resonant actuator may vibrate in response to userinteraction with the human-machine interface to mimic to the user thefeel of a mechanical button click.

Force sensors thus detect forces on the device to determine userinteraction, e.g. touches, presses, or squeezes of the device. There isa need to provide systems to process the output of such sensors whichbalances low power consumption with responsive performance.

There is a need in the industry for sensors to detect user interactionwith a human-machine interface, wherein such sensors and related sensorsystems provide acceptable levels of sensor sensitivity, powerconsumption, and size. There is also a need in the industry to provideforce sensor systems with improved operation over a range of operatingenvironments.

SUMMARY

According to a first aspect of the present disclosure, there is provideda control method for a force sensor system used to define at least onevirtual button, the control method comprising the steps of: receiving aforce sensor input; determining a gradient of the force sensor input;and comparing the determined gradient to a gradient threshold todetermine a user press event of a virtual button.

According to a second aspect of the present disclosure, there isprovided a control method for a force sensor system used to define atleast one virtual button, the control method comprising the steps of:receiving a force sensor input; determining a gradient of the forcesensor input; and comparing the determined gradient to a firstre-calibration threshold to determine a re-calibration requirement ofthe force sensor system.

According to a third aspect of the present disclosure, there is provideda control method for a force sensor system used to define at least onevirtual button, the control method comprising the steps of: receiving aforce sensor input; determining first and second derivatives of theforce sensor input to provide velocity and acceleration values; mappingthe velocity and acceleration values to a 2D representation; andperforming quadrant tracking or state space tracking of the 2Drepresentation of the velocity and acceleration values to determine if auser press event has occurred.

According to a fourth aspect of the present disclosure, there isprovided a method of controlling a force sensor system to define atleast one button implemented by at least one force sensor, the methodcomprising: receiving a force sensor input; determining a gradient ofthe force sensor input; and controlling the force sensor system based onthe determined gradient.

Any of the aforementioned aspects may be employed in combination.

According to a fifth aspect of the present disclosure, there is provideda force sensor system, comprising: at least one force sensor; and acontroller connected to the at least one force sensor and configured tocarry out the method of any of the aforementioned aspects.

According to a sixth aspect of the present disclosure, there is provideda host device comprising the force sensor system according to theaforementioned fifth aspect.

Computer program aspects corresponding to the method aspects areenvisaged, as are (non-transitory) storage medium aspects storingcomputer programs of the computer program aspects.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made, by way of example only, to the accompanyingdrawings, of which:

FIG. 1 illustrates a block diagram of selected components of an examplemobile device;

FIG. 2 is a graph showing an example output of a resistive force sensorsystem;

FIG. 3 presents graphs showing example outputs of a resistive forcesensor system;

FIG. 4 is a graph illustrating an example input from a force sensor overtime, during a series of user press events;

FIG. 5 presents graphs showing example outputs of a resistive forcesensor system;

FIG. 6 presents a graph corresponding to the lower graph in FIG. 5;

FIG. 7A is a schematic diagram of a control method which could beoperated by the force sensor system to determine when to re-calibrate;

FIG. 7B presents graphs showing example outputs of a resistive forcesensor system, useful for understanding an application of the method ofFIG. 7A;

FIG. 8 presents graphs showing example outputs of a resistive forcesensor system where a force input signal is generated by a force sensorsubjected to a user press;

FIG. 9 is a graph showing acceleration and velocity signals of FIG. 8plotted against one another;

FIG. 10 is a graph corresponding to that of FIG. 9 but showing theconcept of a “noise box”;

FIG. 11 is a schematic diagram of a control method which could beoperated by the force sensor system to determine when a press event hasoccurred; and

FIGS. 12A to 12D are graphs depicting stages in an exampleimplementation of the control method of FIG. 11.

DETAILED DESCRIPTION

The description below sets forth example embodiments according to thisdisclosure. Further example embodiments and implementations will beapparent to those having ordinary skill in the art. Further, thosehaving ordinary skill in the art will recognize that various equivalenttechniques may be applied in lieu of, or in conjunction with, theembodiments discussed below, and all such equivalents should be deemedas being encompassed by the present disclosure.

FIG. 1 illustrates a block diagram of selected components of an examplemobile device 102, in accordance with embodiments of the presentdisclosure.

As shown in FIG. 1, mobile device 102 may comprise an enclosure 101, acontroller 103, a memory 104, a force sensor or force sensor system 105,a microphone 106, a linear resonant actuator (LRA) 107, a radiotransmitter/receiver 108, a speaker 110, and an integrated haptic system112. It will be understood that any suitable vibrational actuatorsarranged to provide a haptic vibration effect (e.g., rotationalactuators such as ERMs, vibrating motors, etc.) may be used as analternative to or in addition to the LRA 107.

Enclosure 101 may comprise any suitable housing, casing, or otherenclosure for housing the various components of mobile device 102.Enclosure 101 may be constructed from plastic, metal, and/or any othersuitable materials. In addition, enclosure 101 may be adapted (e.g.,sized and shaped) such that mobile device 102 is readily transported ona person of a user of mobile device 102. Accordingly, mobile device 102may include but is not limited to a smart phone, a tablet computingdevice, a handheld computing device, a personal digital assistant, anotebook computer, a video game controller, a headphone or earphone orany other device that may be readily transported on a person of a userof mobile device 102. While FIG. 1 illustrates a mobile device, it willbe understood that the illustrated systems may be utilized in otherdevice types, e.g. user-interactable display technology, automotivecomputing systems, etc.

Controller 103 may be housed within enclosure 101 and may include anysystem, device, or apparatus configured to interpret and/or executeprogram instructions and/or process data, and may include, withoutlimitation a microprocessor, microcontroller, digital signal processor(DSP), application specific integrated circuit (ASIC), or any otherdigital or analog circuitry configured to interpret and/or executeprogram instructions and/or process data. In some embodiments,controller 103 interprets and/or executes program instructions and/orprocesses data stored in memory 104 and/or other computer-readable mediaaccessible to controller 103.

Memory 104 may be housed within enclosure 101, may be communicativelycoupled to controller 103, and may include any system, device, orapparatus configured to retain program instructions and/or data for aperiod of time (e.g., computer-readable media). Memory 104 may includerandom access memory (RAM), electrically erasable programmable read-onlymemory (EEPROM), a Personal Computer Memory Card InternationalAssociation (PCMCIA) card, flash memory, magnetic storage, opto-magneticstorage, or any suitable selection and/or array of volatile ornon-volatile memory that retains data after power to mobile device 102is turned off.

Microphone 106 may be housed at least partially within enclosure 101,may be communicatively coupled to controller 103, and may comprise anysystem, device, or apparatus configured to convert sound incident atmicrophone 106 to an electrical signal that may be processed bycontroller 103, wherein such sound is converted to an electrical signalusing a diaphragm or membrane having an electrical capacitance thatvaries as based on sonic vibrations received at the diaphragm ormembrane. Microphone 106 may include an electrostatic microphone, acondenser microphone, an electret microphone, a microelectromechanicalsystems (MEMs) microphone, or any other suitable capacitive microphone.

Radio transmitter/receiver 108 may be housed within enclosure 101, maybe communicatively coupled to controller 103, and may include anysystem, device, or apparatus configured to, with the aid of an antenna,generate and transmit radio-frequency signals as well as receiveradio-frequency signals and convert the information carried by suchreceived signals into a form usable by controller 103. Radiotransmitter/receiver 108 may be configured to transmit and/or receivevarious types of radio-frequency signals, including without limitation,cellular communications (e.g., 2G, 3G, 4G, 5G, LTE, etc.), short-rangewireless communications (e.g., BLUETOOTH), commercial radio signals,television signals, satellite radio signals (e.g., GPS), WirelessFidelity, etc.

A speaker 110 may be housed at least partially within enclosure 101 ormay be external to enclosure 101, may be communicatively coupled tocontroller 103, and may comprise any system, device, or apparatusconfigured to produce sound in response to electrical audio signalinput. In some embodiments, a speaker may comprise a dynamicloudspeaker, which employs a lightweight diaphragm mechanically coupledto a rigid frame via a flexible suspension that constrains a voice coilto move axially through a cylindrical magnetic gap. When an electricalsignal is applied to the voice coil, a magnetic field is created by theelectric current in the voice coil, making it a variable electromagnet.The coil and the driver's magnetic system interact, generating amechanical force that causes the coil (and thus, the attached cone) tomove back and forth, thereby reproducing sound under the control of theapplied electrical signal coming from the amplifier.

The force sensor 105 may be housed within, be located on or form part ofthe enclosure 101, and may be communicatively coupled to the controller103. Each force sensor of a device 105 may include any suitable system,device, or apparatus for sensing a force, a pressure, or a touch (e.g.,an interaction with a human finger) and for generating an electrical orelectronic signal in response to such force, pressure, or touch. In someembodiments, such electrical or electronic signal may be a function of amagnitude of the force, pressure, or touch applied to the force sensor.In these and other embodiments, such electronic or electrical signal maycomprise a general-purpose input/output signal (GPIO) associated with aninput signal to which haptic feedback is given.

Example force sensors 105 may include or comprise: capacitivedisplacement sensors, inductive force sensors, strain gauges,piezoelectric force sensors, force sensing resistors, piezoresistiveforce sensors, thin film force sensors, and quantum tunnelingcomposite-based force sensors.

In some arrangements, other types of sensor may be employed. Forpurposes of clarity and exposition in this disclosure, the term “force”as used herein may refer not only to force, but to physical quantitiesindicative of force or analogous to force, such as, but not limited to,pressure and touch.

Linear resonant actuator 107 may be housed within enclosure 101, and mayinclude any suitable system, device, or apparatus for producing anoscillating mechanical force across a single axis. For example, in someembodiments, linear resonant actuator 107 may rely on an alternatingcurrent voltage to drive a voice coil pressed against a moving massconnected to a spring. When the voice coil is driven at the resonantfrequency of the spring, linear resonant actuator 107 may vibrate with aperceptible force. Thus, linear resonant actuator 107 may be useful inhaptic applications within a specific frequency range.

While, for the purposes of clarity and exposition, this disclosure isdescribed in relation to the use of linear resonant actuator 107, it isunderstood that any other type or types of vibrational actuators (e.g.,eccentric rotating mass actuators) may be used in lieu of or in additionto linear resonant actuator 107. In addition, it is also understood thatactuators arranged to produce an oscillating mechanical force acrossmultiple axes may be used in lieu of or in addition to linear resonantactuator 107. A linear resonant actuator 107, based on a signal receivedfrom integrated haptic system 112, may render haptic feedback to a userof mobile device 102 for at least one of mechanical button replacementand capacitive sensor feedback.

Integrated haptic system 112 may be housed within enclosure 101, may becommunicatively coupled to force sensor 105 and linear resonant actuator107, and may include any system, device, or apparatus configured toreceive a signal from force sensor 105 indicative of a force applied tomobile device 102 (e.g., a force applied by a human finger to a virtualbutton of mobile device 102) and generate an electronic signal fordriving linear resonant actuator 107 in response to the force applied tomobile device 102.

Although specific example components are depicted above as beingintegral to mobile device 102 (e.g., controller 103, memory 104, userinterface 105, microphone 106, radio transmitter/receiver 108,speakers(s) 110), a mobile device 102 in accordance with this disclosuremay comprise one or more components not specifically enumerated above.For example, although FIG. 1 depicts certain user interface components,mobile device 102 may include one or more other user interfacecomponents in addition to those depicted in the above figure, includingbut not limited to a keypad, a touch screen, and a display, thusallowing a user to interact with and/or otherwise manipulate mobiledevice 102 and its associated components.

In addition, it will be understood that the device may be provided withadditional input sensor devices or transducers, for exampleaccelerometers, gyroscopes, cameras, or other sensor devices.

Some force sensor systems are sensitive to variations in temperature (orother properties of the operating environment such as pressure). Forexample, for resistive force sensor systems where a bias voltage isapplied to the sensors, changes in temperature can create changes in thebias of the force signal, resulting in changes to the baseline ofoperation of the sensor system.

FIG. 2 is a graph showing an example output of a resistive force sensorsystem as the system temperature increases over time. The output signalis shown as an analogue voltage signal, in mV.

The upper line illustrates the output signal (Force signal), with thesignal peaks indicating the occurrence of touch events detected by thesensor system. The lower line (Baseline tracking) illustrates the outputof a baseline tracking system, to monitor for changes in the biasapplied to the resistive force sensor system. As can be seen, theincreasing temperature of the system results in a steadily increasingbias (baseline) of the system.

It is noted that depending on the force sensor system setup (i.e. anactual implementation), and for example on the type/structure of themobile device 102 comprising the system, it may be that an increasingtemperature of the system results in a steadily increasing bias(baseline) of the system (as above) or conversely a decreasing bias(baseline) of the system. The present disclosure will be understoodaccordingly. In either case, the bias (baseline) of the system maychange with temperature (or another environmental factor).

Additionally or alternatively, the sensitivity of the sensors (such asforce sensor 105) themselves can change with changes in temperature,with an increase (or decrease) in temperature resulting in a reductionin sensitivity.

An issue with force sensor systems can arise when a portion of a devicesuch as device 102, e.g. a frame or casing of a mobile device such asenclosure 101, is at a relatively hot temperature (e.g. 60 degreesCelsius), and where a user touches the device with a finger at normalbody temperature (e.g. 37 degrees Celcius). This can result in atemperature difference between locations on the device, which maytranslate into temperature variations in a force sensor system. Forsensor systems using an arrangement of multiple force sensors (such asforce sensor 105), e.g. resistive force sensors arranged in a WhetstoneBridge configuration or similar, the temperature variation can occurbetween different portions of the sensor, creating a temporary baselinedrift.

FIG. 3 presents graphs showing example outputs of a resistive forcesensor system (force sensor solution) where a force input signal(corresponding to the output signal in

FIG. 2) is generated by a force sensor such as force sensor 105subjected to temperature variation due to a hot frame/cold finger usecase as described above.

The uppermost graph shows the force input signal over time. The forceinput signal is shown as an analogue signal, expressed in N (Newtons).It will be appreciated that analogue voltage signals received from aforce sensor such as force sensor 105 (such as the output signal in FIG.2) may be converted into corresponding force input signals expressed inunits of force (such as the force input signal in FIG. 3).

The input is compared against fixed thresholds (shown in the upper graphas TH rise and TH fall) to determine a rising edge (TH rise) and afalling edge (TH fall) of a user touch or press event.

The middle graph shows the result of a comparison over time of the forceinput signal against the thresholds TH rise and TH fall, the resultbeing a binary output of logic 1 for a rise flag when the force inputsignal rises above (or crosses in an upward direction) the threshold THrise and a binary output of logic 1 for a fall flag when the force inputsignal falls below (or crosses in a downward direction) the threshold THfall. The rise flag and fall flag signals are otherwise at logic 0.

The lowermost graph shows the result of state detection logic performedover time based on the flag signals. The available states indicated bythe state signal shown in this example are “single tap”, “long push”,“double push”, “single push” and “idle detection”, e.g. corresponding tocommon user inputs (or lack of inputs) in relation to a mobile device102 such a smartphone. The state signal indicates the “idle detection”state in this example unless one of the other states is detected, inwhich case that state is indicated.

In this case, even though five individual presses are performed by auser (as indicated by the five peaks of the force input signal in theuppermost graph), due to the increase in the baseline due to thetemperature variation only a long press is detected (as indicated in thelowermost graph) instead of five individual presses.

A gradient release threshold method intended to address the above issuewill now be considered. In overview, it is proposed to analyze thegradient of a force input signal, i.e. its rate of change with respectto time or its first derivative with respect to time (first timederivative), and to use the gradient to detect the release of a buttonimplemented by one or more force sensors, which may be considered avirtual button, and/or to trigger a recalibration of the force sensorsystem.

Here, the release of the button may be considered the process of theuser retracting a finger (or stylus or other body part or similar) fromthe surface in respect of which the force sensor or sensors aremeasuring an applied force, so that the measured applied force reducesfrom a relatively high level (corresponding to a press or push of thebutton) to a relatively low level (corresponding to the button no longerbeing pressed or pushed, i.e. the end of the press or push).Recalibration may be understood as the process of setting a baselinevalue to, or based on, the current force input value.

FIG. 4 is a graph illustrating an example input from a force sensor(i.e. a force input signal) over time, during a series of user pressevents. Thus, although not shown explicitly in FIG. 4, it can be assumedthat the graph has axes corresponding to those in the uppermost graph inFIG. 3.

The gradient of the user press event when the button is pushed(indicated by the rising line superimposed on the first rising edge ofthe input signal) is approximately the same (in magnitude) as thegradient when the button is released (indicated by the falling linesuperimposed on the first falling edge of the input signal).

It can be seen that the gradient for the push event (i.e. when theapplied force is increased from a non-pushed state) is positive and thegradient for the release event (i.e. when the applied force is decreasedback to the non-pushed state) is negative. Accordingly, once the press(or push) is detected (e.g. based on comparison of the input with a risethreshold such as TH rise in FIG. 3 or based on a comparison of thegradient with a positive gradient threshold), the release can bedetected by applying a (negative) gradient threshold to the negativegradient, optionally and a force level threshold to the applied forceusing an OR operation. If either of these conditions are met, a releaseflag can be triggered. That is, if either the applied force falls belowthe force level threshold or the falling gradient falls below (i.e.becomes more negative than) the gradient threshold, then the virtualbutton has been released. Once the virtual button has been released, abaseline tracking system may be then activated.

FIG. 5 presents graphs showing example outputs of a resistive forcesensor system.

The upper graph shows the force sensor inputs (force input signals) overtime in respect of four (virtual) buttons for a series of user pressevents which occur in respect of two of those buttons. The force inputsignals are shown as analogue signals, expressed in N in line with FIG.3. The indication “baseline removed” indicates that there is no baselinetrace present, in contrast for example to FIG. 2. However, it will beappreciated that the baseline is being shifted (and not corrected for)due to a change in temperature, e.g. associated with the user pressevents.

The lower graph shows the instantaneous gradient of the input signalsshown in the upper graph. Thus, the gradient signals are shown asanalogue signals, expressed in N/s. The gradient threshold (fordetecting a release event) is selected such that when the instantaneousgradient falls below the gradient threshold, a release event of thevirtual button is detected. In the illustrated example, a suitablerelease threshold of e.g. −5 N/s would detect the release of the virtualbutton for each of the user press events. It will be understood that thethreshold may be dependent on the stiffness of the device chassis orframe. Accordingly, for different device chassis or frameconfigurations, the release threshold may be set to a different level.

FIG. 6 presents a graph corresponding to the lower graph in FIG. 5. In apreferred aspect, a smoothing filter is applied to the gradient signal,to provide a smoothed gradient with the removal of high frequency noisefrom the signal, as indicated. The smoothed gradient signal may then beused in the methods disclosed herein, in place of or in addition to theunsmoothed gradient signal. Such a smoothed gradient may be provided byapplying a low-pass filtering of the gradient signal.

Additionally or alternatively, the analysis of the falling gradient maybe used as part of a system to trigger a re-calibration of a forcesensor system.

In a preferred aspect, the re-calibration may be triggered if thegradient is lower than the negative threshold. However, the point wherethe system is re-calibrated is not when the gradient is lower than thenegative threshold, rather the re-calibration is performed when thegradient is larger than a second threshold, to ensure that there-calibration will occur at the correct point.

For example, it may be desirable to re-calibrate once the gradient hasbecome more negative than the negative threshold (part of a releaseevent) and then risen up to become 0 (indicating the end of the releaseevent). Baseline re-calibration may have the effect of re-calibratingthe force input signal back to indicating a zero value (0 N) at thatpoint, i.e. for that input from the force sensor(s), in this case whenthe gradient is also zero (0 N/s).

FIG. 7A is a schematic diagram of a control method which could beoperated by the force sensor system (or the device 102 having thatsystem) to determine when to re-calibrate.

Initially a flag gradHit is set to 0, and a series of samples arereceived from the force sensor system. The samples (“Force”) arecompared to a noise threshold TH_noise (Force>TH_noise?). The noisethreshold TH_noise could be the same as, or replaced with, the thresholdTH rise in FIG. 3. If the samples are below the noise threshold, thenthe flag gradHit is set to 0 and the process re-started. If the samples(i.e. sample values) are above the noise threshold, then the flaggradHit is checked to see if it has been set to 1.

If gradHit is at 0, then the gradient of the force signal (“gradient”)is compared to the falling gradient threshold gradLowTH(gradient<gradLowTH?). If the gradient of the falling edge of the forcesignal is below the falling gradient threshold, then this indicates thata re-calibration is required, and the flag gradHit is set to 1. In oneexample, the falling gradient threshold is set at a level of −5 N/s. Thefalling gradient here could be set at a level lower than (i.e. morenegative than, and thus having a larger absolute value than) that usedto detect a release event, i.e. to detect a “very” negative gradientwhich may indicate the need for re-calibration.

The gradient of the falling edge of the force signal is compared to asecond gradient threshold gradHighTh (gradient>gradHighTh?), todetermine if the re-calibration can be performed. If the gradient isabove (or at) the second threshold, e.g. 0 N/s, then the re-calibrationof the force sensor system can be triggered. If the gradient is belowthe second threshold, then a further set of samples are received, and ifthe samples are above the noise threshold (TH_noise) and the gradHitflag is set, then if the gradient is above the second threshold there-calibration can be triggered.

The comparison of the gradient with two separate thresholds allows forthe detection of a required re-calibration, and ensures that there-calibration is performed at the correct point of the force sensorsystem operation (e.g. when the gradient is zero after a touch event).

A further step could be interjected between the successful comparison ofthe gradient to the second gradient threshold (gradient>gradHighTh?=yes)and the triggering of the re-calibration. For example, a comparisoncould be made between the samples (“Force”) and the fall threshold THfall of FIG. 3 to see if the samples are greater than that threshold(Force>TH fall?). If the samples are greater than that threshold(Force>TH fall?=yes) then the re-calibration may be triggered. Otherwise(Force>TH fall?=no), the re-calibration may not be triggered as there-calibration may not be necessary when the samples are at such a lowlevel.

FIG. 7B presents graphs showing example outputs of a resistive forcesensor system, useful for understanding an application of the method ofFIG. 7A.

20

The upper graph corresponds to the upper graph of FIG. 5, and the lowergraph corresponds to the graph of FIG. 6.

Thus, the force sensor inputs (force input signals) over time are shownin the upper graph in respect of four (virtual) buttons for a series ofuser press events which occur in respect of two of those buttons. Thelower graph shows the instantaneous gradient of the input signals shownin the upper graph, smoothed with a smoothing filter.

Unlike the graphs of FIGS. 5 and 6, however, the method of FIG. 7A hasbeen applied. Otherwise, all of these graphs correspond to the same rawdata (i.e. received from one or more force sensors). The indication“baseline removed” again indicates that there is no baseline tracepresent, in contrast for example to FIG. 2. However, it will beappreciated that although the baseline is being shifted as in FIG. 5, itis being corrected for by virtue of the method of FIG. 7A.

As indicated in the upper graph of FIG. 7B, at around the point where arelease event is detected, a re-calibration has been triggered and thevalue of the force input signal concerned is re-calibrated to show a 0 Nvalue (a step change down to 0 N can be seen).

This re-calibration could be applied only to the force input signalconcerned (the one which has triggered the re-calibration) or could beapplied to a plurality or all of the force input signals together.

Note that each “force input signal” represented in e.g. FIG. 7Brepresents the force on the button concerned, but the button may beimplemented with multiple force sensors. Therefore, if the button isimplemented with multiple force sensors (e.g. two force sensors) and itneeds to be re-calibrated, then the raw sensor signals from the forcesensors corresponding to the button may be re-calibrated. In general, itmay be that two force sensors are used per one button (i.e. a 2:1mapping of force sensors to buttons). That is, the signals per button(e.g. plotted in FIG. 7B) may be created by a weighted average of tworaw sensor signals from the force sensors concerned.

20

The re-calibration can be seen to occur three times in FIG. 7B, and thedifference between the upper graphs of FIGS. 5 and 7B is readilyapparent in this respect.

A press dynamics method intended to address the issue mentioned earlierwill now be considered. This method may be considered part of, anaddition to, or an alternative of the gradient release threshold method.

In overview, it is proposed to analyze the dynamics of the force sensorsignal, in particular by quadrant tracking of the first and secondderivatives (i.e. velocity and acceleration), to detect a user pressevent. In this approach, presses and taps can be traceable regardlessthe bias of the signal (i.e. baseline tracking may not be needed, or atleast not to the same degree of accuracy).

Here, the terms “velocity” and “acceleration” will be used forconvenience (i.e. by analogy to position-based measures) to indicate thefirst and second derivatives of the force sensor signal (with respect totime), respectively.

FIG. 8 presents graphs showing example outputs of a resistive forcesensor system (force sensor solution), in particular where a force inputsignal (corresponding to the output signal in FIG. 2) is generated by aforce sensor subjected to a user press.

The uppermost plot shows the force input signal over time. The forceinput signal is shown as an analogue signal expressed in N in line withFIG. 3. The middle plot shows the first derivative of the force inputsignal (indicated as “velocity”). The lowermost plot shows the secondderivative of the force input signal (indicated as “acceleration”).

Thus, a series of samples of a force signal from a force sensor arereceived, which provide the force profile of a user press as indicatedin the top plot of FIG. 8. The first and second derivatives arecalculated to provide the velocity and acceleration of the forceprofile.

The press signal is plotted to indicate the 4 different stages happeningin a press:

-   1. The first section (first stage) of the press is indicated as    Stage 1 (Quadrant I). It represents when the signal goes from    minimum absolute velocity to the maximum velocity with the    acceleration moving from the maximum to zero.-   2. The second section (second stage) of the press is indicated as    Stage 2 (Quadrant IV). This section displays the signal going from    maximum velocity to zero and consequently the acceleration moving to    the minimum value.-   3. The third section (third stage) of the press is indicated as    Stage 3 (Quadrant III). In here, the velocity is going negative as a    consequence of reducing the force level and the acceleration is    approaching zero.-   4. The fourth section (fourth stage) of the press is indicated as    Stage 4 (Quadrant II).

This is the last section where the minimum velocity approaches zero andthe acceleration is positive.

It will be understood that analyzing the velocity and acceleration ofthe force sensor signal is independent of the initial bias level, andaccordingly such analysis will not be negatively impacted by a changedbias level, e.g. due to temperature changes.

FIG. 9 is a graph showing the acceleration (N/s²) and velocity (N/s)signals of FIG. 8 plotted against one another. That is, the velocity andacceleration can be projected onto a 2D representation, to define aquadrant tracking method to determine that a valid user press event hasoccurred.

In particular, the proposed method tracks the velocity and accelerationto confirm that the sensor signal actually moves through the fourdifferent states (corresponding to the four stages mentioned above)consecutively and in the correct order. For a valid user press event tohave occurred, the system is configured to confirm that the combinedvelocity and acceleration points go from Quadrant I (Stage 1) toQuadrant IV (Stage 2); and then from Quadrant IV (Stage 2) to QuadrantIII (Stage 3); and finally from Quadrant III (Stage 3) to Quadrant II(Stage 4). If such a sequence is followed, accordingly a user pressevent is triggered.

In some instances, it may be acceptable to confirm that the combinedvelocity and acceleration points go through fewer (i.e. a subset of the)stages. For example, from

Quadrant IV (Stage 2) to Quadrant III (Stage 3), or from Quadrant I(Stage 1) to Quadrant II (Stage 4), or from Quadrant I (Stage 1) toQuadrant IV (Stage 2) to Quadrant II (Stage 4). It will be understoodthat the present disclosure extends to confirming progression throughany subset of the sequence depicted in FIGS. 8 and 9 (e.g. omitting oneor two Stages may be acceptable).

Of course, it is not necessary to actually generate such a 2Drepresentation in order to perform quadrant tacking; the graph of FIG. 9is simply helpful for understanding the concept. Pairs of correspondingvelocity and acceleration values (which if plotted on the 2Drepresentation of FIG. 9 based on the FIG. 8 force input signal wouldgenerate the plot of FIG. 9) could be tested against ranges of valueswhich define the quadrants to determine in which quadrant any such pairis. Further, the force input signal of FIG. 8 is an example which givesa convenient circle plot in FIG. 9. In a practical implementation,however, a force input signal would be unlikely to give a true circleplot as in FIG. 9.

FIG. 10 is a graph corresponding to that of FIG. 9 but showing theconcept of a “noise box”. In a further aspect, the system may define a“noise box”, as illustrated by a rectangle (square) in FIG. 10, havingvelocity of between +/− 0.4 N/s and acceleration of between +/− 0.25N/s², by way of example. A force sensor signal (force input signal)having a velocity and acceleration falling within the noise box can beassumed to be noise, with anything falling outside of the noise boxassumed to be part of a force event.

While the noise box is illustrated as a rectangle centered at (0,0) inFIG. 10, it will be understood that other geometries may be used, e.g.an ellipse or an irregular shape. Furthermore, it will be understoodthat the noise box may or may not be centered at (0,0), and thedimensions or boundaries of the noise box may be varied dependent on thesystem characteristics.

Further, it will be understood that although in the example of FIG. 10the dimensions of velocity of between +/− 0.4 N/s and acceleration ofbetween +/− 0.25 N/s² define the square in the centre (indicated asbeing excluded), it may be that a force sensor signal (force inputsignal) having a velocity of between +/−0.4 N/s or (rather than and) anacceleration of between +/− 0.25 N/s² is taken to be noise. In thiscase, the “noise box” may be defined as a cross shape (as also apparentfrom FIG. 10, with the square at its centre) which, in this example, isalso defined by the dimensions of velocity of between +/− 0.4 N/s andacceleration of between +/− 0.25 N/s². Thus, a force sensor signal(force input signal) having a velocity and acceleration falling withinthe (cross-shaped) noise box may be assumed to be noise, with anythingfalling outside of the noise box assumed to be part of a force event.

In addition, it will be understood that the boundaries of the “noisebox” can be dynamically calculated or estimated using a recursiveaveraging technique as an alternative to using fixed thresholds. In sucha situation, the definition of the noise box may be unsupervised in thesense that it may be applied on the voltage domain (without using anysensitivity value knowledge) and without setting any threshold.

FIG. 11 is a schematic diagram of a control method which could beoperated by the force sensor system (or the device 102 having thatsystem) to determine when a press event has occurred.

With reference to FIG. 11, for each new force sample, the first andsecond derivatives are calculated, to determine the velocity andacceleration values. The noise box is then updated with the new samples.A quadrant tracking method is applied to check that the samples followthe quadrant sequence that indicates a user press event has occurred,i.e. the samples move in succession through Quadrant Ito Quadrant IV,from IV to III and finally from III to II. If the sequence is followed,then the system can determine that a user press event has occurred. Ifthe sequence is not followed, then the system can determine that anerror has occurred, or an anomalous output from the force sensor systemhas occurred.

This method allows for the unsupervised detection of force events, andin addition is configured to be independent of incorrect sensitivityestimates.

FIGS. 12A to 12D are graphs depicting stages in an exampleimplementation of the control method of FIG. 11.

Each of FIGS. 12A to 12D comprises an upper and lower plot. In the upperplot an example force input signal is shown over time. The force inputsignal is shown as an analogue signal expressed in N in line with FIG.3. The lower plot shows the corresponding acceleration (N/s²) andvelocity (N/s) signals plotted against one another, but with plots beingmade at discrete sample times (rather than continuously as in the upperplot). Thus, the lower plot appears as a succession of separate samplepoints (dots), each sample point representing a pair of acceleration andvelocity values for a corresponding sample point in the upper plot. Alsoshown in the lower plot is a noise box, with sample points within thebox effectively being ignored when determining whether a press has beendetected.

FIGS. 12A to 12D correspond to four snapshots of the process ofcompleting the plots, in time order. To help in a comparison betweenFIGS. 12A to 12D, the complete force input signal is shown faintly inall four of those Figures as if the process of completing the plots hadbeen carried out for the full 4.5 seconds. Five press events can beidentified. In each of FIGS. 12A to 12D, however, the relevant portionof the force input signal which has been plotted so far is shownemboldened.

Thus, starting with FIG. 12A, the plotting has reached the early stagesof the first press event. In the lower plot the sample points haveprogressed from within the noise box diagonally upwards within QuadrantI, with the current sample point of the snapshot indicated as a cross.Above, the lower plot it is indicated that movement into Quadrant I hasbeen detected (the number 1 is also used to indicate the correspondingstage).

Moving on to FIG. 12B, the plotting has reached near the peak of thefirst press event. In the lower plot the sample points have progresseddownwards and into Quadrant IV, with the current sample point of thesnapshot indicated as a cross. Above the lower plot it is indicated thatthe progression from Quadrant Ito IV has been detected (the numbers 1and 2 are also used to indicate the corresponding stages). Note alsothat the noise box has been updated adaptively, based on the velocityand acceleration values (or the force input signal), in line with FIG.11. Further, although the noise box is shown as a rectangle, the presentimplementation has operated based on the cross-shaped noise boxprinciple explained in connection with FIG. 10, where the indicatedrectangle forms the centre of the cross-shaped noise box. Thus, thesample points in the lower plot have had to progress to below the lowerside of the indicated rectangle (i.e. out of the cross-shaped noise boxor noise region) for the progression into Quadrant II to be recognised.

Moving on to FIG. 12C, the plotting has passed beyond the peak of thefirst press event and the detected force is reducing. In the lower plotthe sample points have progressed to the left and into Quadrant III,with the current sample point of the snapshot indicated as a cross.Above the lower plot it is indicated that the progression from QuadrantI, to Quadrant IV and then Quadrant III has been detected (the numbers1, 2 and 3 are also used to indicate the corresponding stages). Thenoise box has been updated adaptively by a small amount, based on thevelocity and acceleration values (or the force input signal), in linewith FIG. 11. The sample points in the lower plot have had to progressto leftward of the left-hand side of the indicated rectangle for theprogression into Quadrant III to be recognised.

Finally, moving on to FIG. 12D, the plotting has passed towards the endof the first press event. In the lower plot the sample points haveprogressed upwards and into Quadrant II, with the current sample pointof the snapshot indicated as a cross. Above the lower plot it isindicated that the progression from Quadrant I, to Quadrant IV, toQuadrant III and then Quadrant II has been detected (the numbers 1, 2, 3and 4 are also used to indicate the corresponding stages). The noise boxhas been updated adaptively again by a small amount, based on thevelocity and acceleration values (or the force input signal), in linewith FIG. 11. The sample points in the lower plot have had to progressto above the upper side of the indicated rectangle for the progressioninto Quadrant II to be recognised.

With the progression through Quadrants I, IV, Ill and II (stages 1, 2, 3and 4) in that order detected, it has been determined that a user presshas been detected, and this is indicated above the upper plot in FIG.12D, and by a dot marked onto the current sample point in the upper plotitself.

Merely as an example, one possible mechanism or algorithm for adaptivelyupdating the size of the noise box is to define the dimensions of therectangle (e.g. as depicted in FIGS. 12A to 12D) so that the rectanglehas its width extending from −(vel_th[n]* headroom_vel) to+(vel_th[n]*headroom_vel), and its height extending from−(acc_th[n]*headroom_acc) to +(acc_th[n]*headroom_acc), whereheadroom_vel and headroom_acc are chosen velocity and accelerationparameters (which could be constants), and where:

vel[n]=x[n]−x[n−1]

acc[n]=vel[n]−vel[n−1]

vel_th[n]=vel_th[n−1]λ+(1−λ)(abs(vel[n])

acc_th[n]=acc_th[n−1]λ+(1−λ)(abs(acc[n])

where n is the sample number, x[n] is the value of the force inputsignal x at sample n, vel[n] and acc[n] are the first and secondderivatives of the signal x at sample n respectively used to determinethe size of the rectangle, abs indicates the absolute value, and λ is aforgetting factor. Of course, other adaptive, recursive methods will beknown to the skilled person.

It will be understood that the above-described gradient releasethreshold method and the press dynamics method may be independently usedin a force sensor system or may be used in combination to determine theoccurrence of user press events in the system. It will be furtherunderstood that either or both of the methods may be used in combinationwith other force sensor methods, e.g. based on fixed or adaptivethresholds.

In a preferred aspect, the above-described methods are used when thetemperature of the force sensor system exceeds a temperature threshold,e.g. above 50 degrees Celsius. As a result, the force sensor system maybe arranged to receive a temperature input, e.g. from a temperaturesensor provided in the device 102, to control the operation of thevarious methods. For temperatures below such a threshold, standard forcesensor methods may be used, but for temperatures above such a thresholdthe use of one or both of the above methods can prevent the processingof incorrect inputs. It will be understood that standard force sensormethods, e.g. using fixed or adaptive thresholds, may continue to beused for temperatures above the temperature threshold.

It will be understood that the above-described methods may beimplemented in a dedicated control module, for example a processingmodule or DSP. The control module may be provided as an integral part ofthe force sensor system or may be provided as part of a centralizedcontroller such as a central processing unit (CPU) or applicationsprocessor (AP). It will be understood that the control module may beprovided with a suitable memory storage module for storing measured andcalculated data for use in the described processes.

The skilled person will recognise that some aspects of the abovedescribed apparatus (circuitry) and methods may be embodied as processorcontrol code (e.g. a computer program), for example on a non-volatilecarrier medium such as a disk, CD- or DVD-ROM, programmed memory such asread only memory (Firmware), or on a data carrier such as an optical orelectrical signal carrier.

For some applications, such aspects will be implemented on a DSP(Digital Signal Processor), ASIC (Application Specific IntegratedCircuit) or FPGA (Field Programmable Gate Array). Thus the code maycomprise conventional program code or microcode or, for example, codefor setting up or controlling an ASIC or FPGA. The code may alsocomprise code for dynamically configuring re-configurable apparatus suchas re-programmable logic gate arrays. Similarly, the code may comprisecode for a hardware description language such as Verilog™ or VHDL. Asthe skilled person will appreciate, the code may be distributed betweena plurality of coupled components in communication with one another.Where appropriate, such aspects may also be implemented using coderunning on a field-(re)programmable analogue array or similar device inorder to configure analogue hardware.

Embodiments may be implemented in a host device, especially a portableand/or battery powered host device such as a mobile computing device forexample a laptop or tablet computer, a games console, a remote controldevice, a home automation controller or a domestic appliance including adomestic temperature or lighting control system, a toy, a machine suchas a robot, an audio player, a video player, a headphone or earphone, ora mobile telephone for example a smartphone. It will be understood thatembodiments may be implemented as part of any suitable human-machineinterface system, for example on a home appliance or in a vehicle orinteractive display. There is further provided a host deviceincorporating the above-described system.

There is further provided a control method for a sensor system asdescribed above.

It should be understood—especially by those having ordinary skill in theart with the benefit of this disclosure—that the various operationsdescribed herein, particularly in connection with the figures, may beimplemented by other circuitry or other hardware components. The orderin which each operation of a given method is performed may be changed,and various elements of the systems illustrated herein may be added,reordered, combined, omitted, modified, etc. It is intended that thisdisclosure embrace all such modifications and changes and, accordingly,the above description should be regarded in an illustrative rather thana restrictive sense.

Similarly, although this disclosure makes reference to specificembodiments, certain modifications and changes can be made to thoseembodiments without departing from the scope and coverage of thisdisclosure. Moreover, any benefits, advantages, or solutions to problemsthat are described herein with regard to specific embodiments are notintended to be construed as a critical, required, or essential featureor element. It should be noted that the above-mentioned embodimentsillustrate rather than limit the invention, and that those skilled inthe art will be able to design many alternative embodiments withoutdeparting from the scope of the appended claims. The word “comprising”does not exclude the presence of elements or steps other than thoselisted in the claim, “a” or “an” does not exclude a plurality, and asingle feature or other unit may fulfil the functions of several unitsrecited in the claims. Any reference numerals or labels in the claimsshall not be construed so as to limit their scope.

Further embodiments likewise, with the benefit of this disclosure, willbe apparent to those having ordinary skill in the art, and suchembodiments should be deemed as being encompassed herein.

As used herein, when two or more elements are referred to as “coupled”to one another, such term indicates that such two or more elements arein electronic communication or mechanical communication, as applicable,whether connected indirectly or directly, with or without interveningelements.

This disclosure encompasses all changes, substitutions, variations,alterations, and modifications to the example embodiments herein that aperson having ordinary skill in the art would comprehend. Similarly,where appropriate, the appended claims encompass all changes,substitutions, variations, alterations, and modifications to the exampleembodiments herein that a person having ordinary skill in the art wouldcomprehend. Moreover, reference in the appended claims to an apparatusor system or a component of an apparatus or system being adapted to,arranged to, capable of, configured to, enabled to, operable to, oroperative to perform a particular function encompasses that apparatus,system, or component, whether or not it or that particular function isactivated, turned on, or unlocked, as long as that apparatus, system, orcomponent is so adapted, arranged, capable, configured, enabled,operable, or operative. Accordingly, modifications, additions, oromissions may be made to the systems, apparatuses, and methods describedherein without departing from the scope of the disclosure. For example,the components of the systems and apparatuses may be integrated orseparated. Moreover, the operations of the systems and apparatusesdisclosed herein may be performed by more, fewer, or other componentsand the methods described may include more, fewer, or other steps.Additionally, steps may be performed in any suitable order. As used inthis document, “each” refers to each member of a set or each member of asubset of a set.

Although exemplary embodiments are illustrated in the figures anddescribed below, the principles of the present disclosure may beimplemented using any number of techniques, whether currently known ornot. The present disclosure should in no way be limited to the exemplaryimplementations and techniques illustrated in the drawings and describedabove.

Unless otherwise specifically noted, articles depicted in the drawingsare not necessarily drawn to scale.

All examples and conditional language recited herein are intended forpedagogical objects to aid the reader in understanding the disclosureand the concepts contributed by the inventor to furthering the art, andare construed as being without limitation to such specifically recitedexamples and conditions. Although embodiments of the present disclosurehave been described in detail, it should be understood that variouschanges, substitutions, and alterations could be made hereto withoutdeparting from the spirit and scope of the disclosure.

Although specific advantages have been enumerated above, variousembodiments may include some, none, or all of the enumerated advantages.Additionally, other technical advantages may become readily apparent toone of ordinary skill in the art after review of the foregoing figuresand description.

To aid the Patent Office and any readers of any patent issued on thisapplication in interpreting the claims appended hereto, applicants wishto note that they do not intend any of the appended claims or claimelements to invoke 35 U.S.C. § 112(f) unless the words “means for” or“step for” are explicitly used in the particular claim.

Aspects of the system may be defined by the following numberedstatements:

-   1. There is provided a control method for a force sensor system used    to define at least one virtual button, the control method comprising    the steps of:

receiving a force sensor input;

determining a gradient of the force sensor input; and

comparing the determined gradient to a gradient threshold to determine auser press event of a virtual button.

-   2. Preferably, the method comprises the step of comparing the    determined gradient to a falling gradient threshold to determine a    release event of a virtual button.-   3. In one aspect, the falling gradient threshold is selected based    on characteristic properties of a device having the force sensor    system, e.g. the stiffness of a chassis or frame of such a device.    In a preferred aspect, the falling gradient threshold is set at    approximately −5 N/s.-   4. Additionally or alternatively, there is provided a first control    method for a force sensor system used to define at least one virtual    button, the control method comprising the steps of:

receiving a force sensor input;

determining a gradient of the force sensor input; and

comparing the determined gradient to a first re-calibration threshold todetermine a re-calibration requirement of the force sensor system.

-   5. Preferably, the first re-calibration threshold is a negative    value. In a preferred aspect, the first re-calibration threshold is    selected as the falling gradient threshold as described above. In    one aspect, the first re-calibration threshold is set at    approximately −5 N/s.-   6. Preferably, responsive to a determination that a re-calibration    is required, the method comprises the step of comparing the    determined gradient to a second re-calibration threshold to trigger    a re-calibration of the force sensor system.-   7. Preferably, the second re-calibration threshold is set at a level    higher than the first re-calibration threshold. Preferably, the    second re-calibration threshold is approximately a zero value, e.g.    0 N/s. Alternatively, the second re-calibration threshold may be a    positive value, or a negative value close to zero, e.g. −1 N/s.

As the second threshold is defined at a positive or zero value,accordingly the re-calibration of the system will be performed at thecorrect point for accurate system operation.

-   8. Preferably, the method comprises determining a smoothed gradient    of the force sensor input, preferably by performing a low pass    filtering of the gradient signal, wherein the steps of comparing are    performed using the smoothed gradient.

Providing a smoothed gradient removes high-frequency noise from thegradient signal, to allow for more accurate comparison of the gradientto the relevant thresholds.

-   9. Additionally or alternatively, there is provided a second control    method for a force sensor system used to define at least one virtual    button, the control method comprising the steps of:

receiving a force sensor input;

determining first and second derivatives of the force sensor input toprovide velocity and acceleration values;

mapping the velocity and acceleration values to a 2D representation; and

performing quadrant tracking or state space tracking of the 2Drepresentation of the velocity and acceleration values to determine if auser press event has occurred.

-   10. Preferably, the method comprises the step of determining a user    press event has occurred if the quadrant tracking follows a defined    sequence.-   11. Preferably, the method comprises the step of determining a user    press event has occurred if the velocity and acceleration values    sequentially progress through first, second, third and fourth    stages, wherein the stages are defined as follows:

First stage: positive velocity, positive acceleration;

Second stage: positive velocity, negative acceleration;

Third stage: negative velocity, negative acceleration; and

Fourth stage: negative velocity, positive acceleration.

-   12. Preferably, the method comprises the step of defining a noise    box as part of a 2D representation, wherein a force sensor input    having velocity and acceleration values falling outside of the noise    box is assumed to be part of a user press event.-   13. Preferably, the noise box is defined as a space at the center of    the 2D representation.-   14. Preferably, the noise box is centered at (0,0) of the 2D    representation.-   15. In one aspect, the noise box is defined as a rectangle having a    velocity value of between +/− 0.4 N/s and an acceleration value of    between +/− 0.25 N/s2. Alternatively, the noise box is dynamically    calculated.-   16. In an alternative aspect, the noise box is defined as an    alternative shape, e.g. an ellipse.-   17. In one aspect, the above-described control methods are performed    together in a force sensor system.-   18. Preferably, at least one of the above-described control methods    comprise:

receiving a temperature level of a force sensor system; and

performing the control method when the temperature level is above atemperature threshold.

-   19. Preferably, the temperature threshold is approximately 50    degrees Celsius.-   20. The temperature threshold may be received from a temperature    sensor provided at the force sensor system, or may be received from    a temperature sensor of a device comprising such a force sensor    system.-   21. Preferably, the above-described control methods are performed in    combination with an alternative force sensor control method to    determine user touch events, e.g. a force sensor control method    using absolute or adaptive thresholds-   22. There is further provided a force sensor system comprising at    least one force sensor and a controller arranged to implement at    least one of the above-described control methods.-   23. Preferably, the at least one force sensor comprises one or more    of the following:

a capacitive displacement sensor,

an inductive force sensor,

a strain gauge,

a piezoelectric force sensor,

a force sensing resistor,

a piezoresistive force sensor,

a thin film force sensor, and

a quantum tunneling composite-based force sensor.

-   24. There is provided a host device comprising a force sensor system    as described above.

Aspects of the present disclosure may also be defined by the followingnumbered statements:

-   S1. A method of controlling a force sensor system to define at least    one button implemented by at least one force sensor, the method    comprising:

receiving a force sensor input;

determining a gradient of the force sensor input; and

controlling the force sensor system based on the determined gradient.

-   S2. The method according to statement S1, wherein:

the force sensor input is received from the at least one force sensor;and/or

the at least one button is a virtual button, optionally defined at alocation on a device other than a location on the device of said atleast one force sensor.

-   S3. The method according to statement S1 or S2, wherein said    gradient is:

a gradient with respect to time; and/or

a first derivative with respect to time; and/or

a first time derivative.

-   S4. The method according to any of the preceding statements, wherein    the control comprises comparing the determined gradient to:

a press-event gradient threshold to determine a user press event of theat least one button; and/or

a falling gradient threshold to determine a release event of the atleast one button; and/or

a first re-calibration threshold to determine a re-calibrationrequirement of the force sensor system.

-   S5. The method according to statement S4, wherein at least one of    the press-event gradient threshold, the falling gradient threshold    and the first re-calibration threshold is a negative gradient    threshold or has a negative value, and is optionally set at a value    corresponding to a detected rate of change of force with respect to    time of approximately −5 N/s.-   S6. The method according to statement S4 or S5, wherein at least one    of the press-event gradient threshold, the falling gradient    threshold and the first re-calibration threshold is based on    characteristic properties of a device having the force sensor    system, such as the stiffness of a chassis or frame of the device.-   S7. The method according to any of statements S4 to S6, wherein the    press-event gradient threshold, the falling gradient threshold and    the first re-calibration threshold, or at least two of those    thresholds, are the same as one another.-   S8. The method according to any of statements S4 to S7, wherein the    method comprises comparing the determined gradient to a second    re-calibration threshold to trigger a re-calibration of the force    sensor system.-   S9. The method according to statement S8, wherein a value of the    second re-calibration threshold is set at a level higher than, or    more positive than, that of the first re-calibration threshold.-   S10. The method according to statement S8 or S9, wherein:

the second re-calibration threshold has a value corresponding to adetected rate of change of force with respect to time of approximately 0N/s; or

the second re-calibration threshold has a positive value or a negativevalue corresponding to a detected rate of change of force with respectto time of close to 0 N/s, such as 1 N/s or −1 N/s.

-   S11. The method according to any of statements S8 to S10, wherein    the method comprises triggering the re-calibration if the determined    gradient crosses the first re-calibration threshold and the second    re-calibration threshold, optionally in that order.-   S12. The method according to any of the preceding statements,    wherein:

the determining a gradient of the force sensor input comprisesdetermining a smoothed gradient of the force sensor input, preferably bydetermining an un-smoothed gradient of the force sensor input andperforming a low-pass filtering of the un-smoothed gradient; and

the comparing is performed using the smoothed gradient.

-   S13. The method according to any of the preceding statements,    comprising:

determining first derivatives and second derivatives of the force sensorinput to provide corresponding first-derivative values andsecond-derivative values; and

controlling the force sensor system based on the first-derivative valuesand the second-derivative values.

-   S14. The method according to statement S13, wherein:

each said derivative is a derivative with respect to time, or a timederivative; and/or

the second derivative is a rate of change of the first derivative withrespect to time; and/or

the first derivative is a first-order derivative and the second derivateis a second-order derivative.

-   S15. The method according to statement S13 or S14, comprising:

comparing the first-derivative values and the second-derivative valuesto threshold values to control the force sensor system.

-   S16. The method according to any of statements S13 to S15,    comprising:

comparing the first-derivative values and the second-derivative valuesto threshold values to determine if a user press event has occurredand/or to determine a re-calibration requirement of the force sensorsystem.

-   S17. The method according to any of statements S13 to 16, wherein    the first-derivative values and the second-derivative values are    determined as successive pairs of (instantaneous) derivative values,    each pair comprising a first-derivative value and a    second-derivative value corresponding to a given value of the force    sensor input or to a given point in time.-   S18. The method according to statement S17, comprising:    -   mapping the pairs of derivative values to a 2D representation;        and    -   performing quadrant tracking or state space tracking with        respect to the 2D representation of the successive pairs of        derivative values to determine if a user press event has        occurred.-   S19. The method according to statement S18, wherein the 2D    representation comprises a plot of first-derivative values against    second-derivative values, or vice versa.-   S20. The method according to statement S18 or S19, wherein the    method comprises determining a user press event has occurred if the    quadrant tracking or state space tracking follows a defined    sequence.-   S21. The method according to any of statements S18 to S20, wherein    the method comprises defining a noise box as part of the 2D    representation,

and wherein:

-   -   force sensor input having first-derivative values and        second-derivative values falling outside of the noise box is        subjected to the quadrant tracking or state space tracking to        determine if the user press event has occurred; and/or    -   pairs of derivative values falling inside the noise box are        excluded from the quadrant tracking or state space tracking.

-   S22. The method according to statement S21, wherein the noise box is    defined as a space at the centre of the 2D representation.

-   S23. The method according to statement S21 or S22, wherein, the    noise box is centred at (0,0) or an origin of the 2D representation.

-   S24. The method according to any of statements S21 to S23, wherein    the noise box is defined as a rectangle, optionally having a    first-derivative value of between +/− 0.4 N/s and a    second-derivative value of between +/− 0.25 N/s2.

-   S25. The method according to any of statements S21 to S24, wherein    the noise box is dynamically calculated.

-   S26. The method according to any of statements S21 to S25, wherein    the noise box is defined as a noise shape, such as an ellipse or    cross.

-   S27. The method according to any of statements S17 to S26, wherein    the method comprises determining that a user press event has    occurred if the successive pairs of first-derivative and    second-derivative values sequentially progress through first,    second, third and fourth stages (in that order), wherein the stages    are defined as follows:

first stage: positive first-derivative value, positive second-derivativevalue;

second stage: positive first-derivative value, negativesecond-derivative value;

third stage: negative first-derivative value, negative second-derivativevalue; and

fourth stage: negative first-derivative value, positivesecond-derivative value.

-   S28. The method according to any of statements S17 to S27, wherein    the method comprises defining a first-derivative noise range as a    range of first-derivative values attributable to noise, and    excluding a pair of first-derivative and second-derivative values    from determining a user press event has occurred if the    first-derivative value of that pair is within the first-derivative    noise range.-   S29. The method according to statement S28, wherein the method    comprises updating the first-derivative noise range dynamically,    optionally based on preceding first-derivative values.-   S30. The method according to any of statements S17 to S29, wherein    the method comprises defining a second-derivative noise range as a    range of second-derivative values attributable to noise, and    excluding a pair of first-derivative and second-derivative values    from determining a user press event has occurred if the    second-derivative value of that pair is within the second-derivative    noise range.-   S31. The method according to statement S30, wherein the method    comprises updating the second-derivative noise range dynamically,    optionally based on preceding second-derivative values.-   S32. The method according to any of statements S17 to S31, wherein    the method comprises defining a noise space as a space defined by    pairs of first-derivative and second-derivative values attributable    to noise, and excluding a pair of first-derivative and    second-derivative values from determining a user press event has    occurred if that pair of first-derivative and second-derivative    values falls within the noise space.-   S33. The method according to statement S32, wherein the method    comprises updating the noise space dynamically, optionally based on    preceding first-derivative values, second-derivative values and/or    pairs of first-derivative and second-derivative values.-   S34. The method according to any of the preceding statements,    comprising:

receiving a temperature level of the force sensor system; and

performing the method (e.g. only) when the temperature level is above atemperature threshold,

optionally comprising determining whether the temperature level is abovethe temperature threshold.

-   S35. The method according to statement S34, wherein the temperature    threshold is approximately 50 degrees Celsius.-   S36. The method according to statement S34 or S35, wherein the    temperature level is received from a temperature sensor of the force    sensor system, or from a temperature sensor of a device comprising    the force sensor system.-   S37. The method according to any of statements S34 to S36,    comprising:

performing said determining and controlling when the temperature levelis above the temperature threshold; and

controlling the force sensor system without using a gradient of theforce sensor input, or without performing said determining, when thetemperature level is not above the temperature threshold.

-   S38. A force sensor system, comprising:

at least one force sensor; and

a controller connected to the at least one force sensor and configuredto carry out the method of any of the preceding statements.

-   S39. The force sensor system according to statement S38, wherein the    at least one force sensor comprises one or more of the following:

a capacitive displacement sensor,

an inductive force sensor,

a strain gauge,

a piezoelectric force sensor,

a force sensing resistor,

a piezoresistive force sensor,

a thin film force sensor, and

a quantum tunneling composite-based force sensor.

-   S40. A host device comprising the force sensor system according to    statement S38 or S39.

1. A method of controlling a force sensor system to define at least onebutton implemented by at least one force sensor, the method comprising:receiving a force sensor input; determining a gradient of the forcesensor input; and controlling the force sensor system based on thedetermined gradient.
 2. The method according to claim 1, wherein thecontrol comprises comparing the determined gradient to: a press-eventgradient threshold to determine a user press event of the at least onebutton; and/or a falling gradient threshold to determine a release eventof the at least one button; and/or a first re-calibration threshold todetermine a re-calibration requirement of the force sensor system. 3.The method according to claim 2, wherein at least one of the press-eventgradient threshold, the falling gradient threshold and the firstre-calibration threshold is a negative gradient threshold or has anegative value, and is optionally set at a value corresponding to adetected rate of change of force with respect to time of approximately−5 N/s.
 4. The method according to claim 2, wherein the method comprisescomparing the determined gradient to a second re-calibration thresholdto trigger a re-calibration of the force sensor system.
 5. The methodaccording to claim 4, wherein a value of the second re-calibrationthreshold is set at a level higher than, or more positive than, that ofthe first re-calibration threshold.
 6. The method according to claim 4,wherein the method comprises triggering the re-calibration if thedetermined gradient crosses the first re-calibration threshold and thesecond re-calibration threshold, optionally in that order.
 7. The methodaccording to claim 1, comprising: determining first derivatives andsecond derivatives of the force sensor input to provide correspondingfirst-derivative values and second-derivative values; and controllingthe force sensor system based on the first-derivative values and thesecond-derivative values.
 8. The method according to claim 7,comprising: comparing the first-derivative values and thesecond-derivative values to threshold values to control the force sensorsystem.
 9. The method according to claim 7, comprising: comparing thefirst-derivative values and the second-derivative values to thresholdvalues to determine if a user press event has occurred and/or todetermine a re-calibration requirement of the force sensor system. 10.The method according to claim 7, wherein the first-derivative values andthe second-derivative values are determined as successive pairs ofderivative values, each pair comprising a first-derivative value and asecond-derivative value corresponding to a given value of the forcesensor input or to a given point in time.
 11. The method according toclaim 10, comprising: mapping the pairs of derivative values to a 2Drepresentation; and performing quadrant tracking or state space trackingwith respect to the 2D representation of the successive pairs ofderivative values to determine if a user press event has occurred. 12.The method according to claim 11, wherein the method comprises defininga noise box as part of the 2D representation, and wherein: a forcesensor input having first-derivative values and second-derivative valuesfalling outside of the noise box is subjected to the quadrant trackingor state space tracking to determine if the user press event hasoccurred; and/or pairs of derivative values falling inside the noise boxare excluded from the quadrant tracking or state space tracking,optionally wherein the noise box is dynamically calculated.
 13. Themethod according to claim 10, wherein the method comprises determiningthat a user press event has occurred if the successive pairs offirst-derivative and second-derivative values sequentially progressthrough first, second, third and fourth stages, wherein the stages aredefined as follows: first stage: positive first-derivative value,positive second-derivative value; second stage: positivefirst-derivative value, negative second-derivative value; third stage:negative first-derivative value, negative second-derivative value; andfourth stage: negative first-derivative value, positivesecond-derivative value.
 14. The method according to claim 10, whereinthe method comprises defining a first-derivative noise range as a rangeof first-derivative values attributable to noise, and excluding a pairof first-derivative and second-derivative values from determining a userpress event has occurred if the first-derivative value of that pair iswithin the first-derivative noise range.
 15. The method according toclaim 10, wherein the method comprises defining a second-derivativenoise range as a range of second-derivative values attributable tonoise, and excluding a pair of first-derivative and second-derivativevalues from determining a user press event has occurred if thesecond-derivative value of that pair is within the second-derivativenoise range.
 16. The method according to claim 10, wherein the methodcomprises defining a noise space as a space defined by pairs offirst-derivative and second-derivative values attributable to noise, andexcluding a pair of first-derivative and second-derivative values fromdetermining a user press event has occurred if that pair offirst-derivative and second-derivative values falls within the noisespace, optionally wherein the method comprises updating the noise spacedynamically, optionally based on preceding first-derivative values,second-derivative values and/or pairs of first-derivative andsecond-derivative values.
 17. The method according to claim 1,comprising: receiving a temperature level of the force sensor system;and performing the method when the temperature level is above atemperature threshold, optionally comprising determining whether thetemperature level is above the temperature threshold.
 18. The methodaccording to claim 17, comprising: performing said determining andcontrolling when the temperature level is above the temperaturethreshold; and controlling the force sensor system without using agradient of the force sensor input, or without performing saiddetermining, when the temperature level is not above the temperaturethreshold.
 19. A control method for a force sensor system used to defineat least one virtual button, the control method comprising the steps of:receiving a force sensor input; determining first and second derivativesof the force sensor input to provide velocity and acceleration values;mapping the velocity and acceleration values to a 2D representation; andperforming quadrant tracking or state space tracking of the 2Drepresentation of the velocity and acceleration values to determine if auser press event has occurred.
 20. A force sensor system such as a hostdevice, comprising: at least one force sensor; and a controllerconnected to the at least one force sensor and configured to carry outthe method of claim 1.